This event is used to create a public house where the party may socialize with the inhabitants of the local demesne (start a fight), share tales of wondrous events (eavesdrop), and sample local concoctions (use your imagination). The party’s options in a tavern are indicated by buttons at the bottom of the screen.
On page 2, you may specify a picture and a page of text which are displayed when the party enters the tavern. You may indicate whether there will be a “Fight” button, and, if so, what event is chained to when the “Fight” button is selected. You may also determine whether the party steps back into the location from which they entered tavern when they are through with the tavern, or whether they remain in the tavern’s location.
On pages 3 and 4, you may enter up to four tavern tales, and, on page three, you may indicate whether the tales are told in sequence, or in a random order. If you wish to have more than four tavern tales, you must place a TAVERN TALES event in a chain BEFORE the TAVERN event.
On page 5, you may indicate whether drinking is allowed at the tavern. If drinking is allowed, you may specify the names of up to five drinks (which must fit on one line and have unique first letters). Each drink has a strength, as shown on page 5; you may select an event to chain to when drinks with strengths totalling 60 or more have been consumed.
TAVERN TALES
This event may be used to provide additional tavern tales for a TAVERN or SMALL TOWN event. The TAVERN TALES event must be placed in a chain BEFORE the TAVERN or SMALL TOWN event. You may enter up to six tavern tales in a TAVERN TALES event.
TELEPORTER
This event functions in exactly the same fashion as a STAIRS event, except that it takes place as the party moves into or LOOKs at the location of the event, whereas a STAIRS event happens when the party attempts to leave an adjoining location to enter the event’s location; thus, in a TELEPORTER, the party will be able see the walls of the location containing the event from the location itself, which is not possible in a STAIRS event. Note that entry point destination selection does not work in IBM v 1.0.
TEMPLE
This event is a temple where the party may pay for healing spells. The party may also be able to donate platinum pieces to a temple, and may be rewarded for their generosity.
On page 2, you may select a picture and enter a page of text to display when the party first enters a temple. You may also specify the highest level of healing spell available at the temple and the cost factor of the healing spells, in comparison to standard temple rates. Note that for the “Fix” button (which automatically heals all possible damage to party members) to be available to the party, the highest spell level must be set to ‘7’ and the cost factor must be set to ‘free’.
On page 2, you may also indicate whether the temple accepts donations, the number of platinum pieces which must be donated before the temple offers a reward (or punishment), and the event which will happen after the indicated number of platinum pieces has been donated. The temple will keep track of the total amount of platinum donated, not just the amount donated at any single visit to the temple, but the chained event will not happen until the party starts to leave the temple after donating the requisite amount of platinum.
On page three you may enter the message which will be displayed whenever the the temple menu is on the screen, such as , “How may we help you?” You may also indicate whether the party returns to the location from which they entered the temple after departing, or whether they remain in the temple location.
TEXT STATEMENT
This event is used to display up to five pages of text. It has the same format as a NPC SAYS event, except that it is not conditional upon the presence of a specific NPC.
TRAINING HALL
This event is a training hall where the party may go up experience levels, replace dead party members, etc. You may specify which classes may be trained at the training hall and how much it costs (per level) to train. You may also select a picture and enter a page of text to display when the party enters the training hall, and you may indicate whether the party returns to the location it came from or remains in the training location when training is completed.
TRANSFER MODULE
This event is used to move the party from one module to another. In form, it is similar to a STAIRS or TELEPORTER event, but there are significant differences.
On page 2, your first choice is whether the event happens when the party is in the event’s location, in the manner of a teleporter, or as the party enters the location, in the manner of stairs. The options related to asking the party whether they wish to transfer modules work in the same fashion as in a STAIRS event. You also have the option of destroying all drow equipment with sunlight as the party transfers to a new module.
The page 3 options are the same as for a STAIRS event, except that you may also specify which module the party is transferring to (selecting an entry point WILL work in IBM v 1.0).
UTILITIES
This event is used for arithmetic and logical operations on variables, and for ending an adventure. You may perform each of the three types of operation in a single UTILITIES event, although it is rather pointless to perform any other operations if you are ending the adventure.
The first type of operation is arithmetic. An arithmetic operation allows you to add, subtract, or store a specific value in the variable you select. Values must be positive integers between 0 and 255. Remember that a value of zero indicates that the party does not possess a given item, while any other value indicates that the party does possess the item.
The second operation is ending the adventure, which exits play. It is recommended that you warn the player before ending the adventure, and provide an opportunity to save the characters in the party, if they are to be allowed further adventures.
The third operation is a multi-item check. This allows you to check whether the party has any or all of any six items and, if they do, give them a seventh item. If you are checking fewer than six items, simply check one of the items several times. This operation may be useful for determining whether the party has completed any of several tasks required to proceed, or whether the party has completed all of the tasks required to proceed, as the case may be.
VAULT
This event is used to create a vault in which the party can store surplus wealth and equipment. Note that all vaults in a given adventure are connected by a hyperspace shunt to the same repository of money and items. In a VAULT event, you may select a picture and enter a page of text to display, and you may specify whether the party returns to the location they came from or remains in the vault location upon leaving the vault.
WHO PAYS
This event is used to allow the player to select a party member to pay a specified price. If a selected party member has sufficient wealth to pay the price, the price is deducted from the party member’s wealth, and the party has succeeded. If the party exits without paying, they have failed.
On page 2, you may select a picture and enter a page of text to display. You may also specify the price which must be paid in platinum pieces, gems, or jewelry (or specify an impossible price) and select a destination for teleportation resulting from success or failure. Furthermore, you may indicate whether any event at the destination happens when the party arrives.
On page 3, you may enter a page of text, which will be displayed if the party pays the price. You may also specify whether another event happens or the party steps back or teleports after paying. On page 4, you have the same options for the case in which the party gives up without paying.
WHO TRIES
This event is used to judge whether the party can succeed at a task by checking the selected party member’s stats or thief skills. You may specify the number of times the party may attempt the task and the consequences of success or repeated failure.
On page 2, you may first select a picture and enter a page of text to display. You may specify the stat or thief skill to check (or specify that the attempt automatically succeeds or fails), indicate whether the stat or skill must equal or exceed a specified value or a die roll (d20 for stats; d100 for thief skills), and specify the number of attempts the party is allowed. You may also select a destination for teleportation resulting from success or failure. Furthermore, you may indicate whether any event at the destination happens when the party arrives. Pages 3 and 4 are used to specify the consequences of success and failure. They have the same format as in a WHO PAYS event.
